🚫 🔍 [Deprecated] Fortinet via Legacy Agent
🚫 Deprecated: This connector has been deprecated and may be removed in future versions.
🔍 Discovered: This item was discovered by scanning the solution folder but is not listed in the Solution JSON file.
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
| Attribute | Value |
|---|---|
| Connector ID | Fortinet |
| Publisher | Fortinet |
| Used in Solutions | Fortinet FortiGate Next-Generation Firewall connector for Microsoft Sentinel |
| Collection Method | AMA |
| Connector Definition Files | Fortinet-FortiGate.json |
The Fortinet firewall connector allows you to easily connect your Fortinet logs with Microsoft Sentinel, to view dashboards, create custom alerts, and improve investigation. This gives you more insight into your organization's network and improves your security operation capabilities.
Additional Information
- 📖 Vendor Documentation: FortiGate Log Message Fields - Complete log field reference with examples
- 🛠️ Device Configuration: Set Fortinet to send Syslog messages in CEF format to port 514 TCP. Replace 'server
' with the Syslog agent IP. See Fortinet Document Library. Learn more
Tables Ingested
This connector ingests data into the following tables:
| Table | Selection Criteria | Transformations | Ingestion API | Lake-Only |
|---|---|---|---|---|
CommonSecurityLog |
DeviceProduct startswith "Fortigate"DeviceVendor == "Fortinet" |
✓ | ✓ | ✓ |
💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.
Permissions
Resource Provider Permissions:
- Workspace (Workspace): read and write permissions are required.
- Keys (Workspace): read permissions to shared keys for the workspace are required. See the documentation to learn more about workspace keys.
Setup Instructions
⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.
1. Linux Syslog agent configuration
Install and configure the Linux agent to collect your Common Event Format (CEF) Syslog messages and forward them to Microsoft Sentinel.
Notice that the data from all regions will be stored in the selected workspace 1.1 Select or create a Linux machine
Select or create a Linux machine that Microsoft Sentinel will use as the proxy between your security solution and Microsoft Sentinel this machine can be on your on-prem environment, Azure or other clouds.
1.2 Install the CEF collector on the Linux machine
Install the Microsoft Monitoring Agent on your Linux machine and configure the machine to listen on the necessary port and forward messages to your Microsoft Sentinel workspace. The CEF collector collects CEF messages on port 514 TCP.
- Make sure that you have Python on your machine using the following command: python --version.
- You must have elevated permissions (sudo) on your machine.
- Run the following command to install and apply the CEF collector::
sudo wget -O cef_installer.py https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/DataConnectors/CEF/cef_installer.py &&sudo python cef_installer.py {0} {1}2. Forward Fortinet logs to Syslog agent
Set your Fortinet to send Syslog messages in CEF format to the proxy machine. Make sure you to send the logs to port 514 TCP on the machine’s IP address.
Copy the CLI commands below and:
- Replace "server <ip address>" with the Syslog agent's IP address.
- Set the "<facility_name>" to use the facility you configured in the Syslog agent (by default, the agent sets this to local4).
- Set the Syslog port to 514, the port your agent uses.
- To enable CEF format in early FortiOS versions, you may need to run the command "set csv disable".
For more information, go to the Fortinet Document Library, choose your version, and use the "Handbook" and "Log Message Reference" PDFs.
- Set up the connection using the CLI to run the following commands::
config log syslogd setting set status enable set format cef set port 514 set server <ip_address_of_Receiver> end
3. Validate connection
Follow the instructions to validate your connectivity:
Open Log Analytics to check if the logs are received using the CommonSecurityLog schema.
It may take about 20 minutes until the connection streams data to your workspace.
If the logs are not received, run the following connectivity validation script:
- Make sure that you have Python on your machine using the following command: python --version
- You must have elevated permissions (sudo) on your machine
- Run the following command to validate your connectivity::
sudo wget -O cef_troubleshoot.py https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/DataConnectors/CEF/cef_troubleshoot.py &&sudo python cef_troubleshoot.py {0}
4. Secure your machine
Make sure to configure the machine's security according to your organization's security policy
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊